Secure communications for wireless mesh network access points

ABSTRACT

Techniques for secure communications among wireless mesh network access points are described herein. According to one embodiment, a wireless mesh network includes multiple wireless mesh access points communicatively coupled to each other via multiple mesh links and multiple end-user clients, each being associated with one of the wireless mesh access points. In response to a packet received at a first mesh access point of the wireless mesh access points from a local end-user client of the first mesh access point destined to another end-user client associated with a second mesh access point of the wireless mesh access points, the packet is routed via a tunneling protocol from the first mesh access point to the second mesh access point. Other methods and apparatuses are also described.

RELATED APPLICATION

This application claims the priority of U.S. Provisional Patent Application No. 60/939,314, filed May 21, 2007, which is incorporated by reference herein in its entirety.

FIELD OF THE INVENTION

The present invention relates generally to wireless networks. More particularly, this invention relates to secure communications for wireless mesh network access points.

BACKGROUND

Wireless mesh networks are gaining popularity because wireless infrastructures are typically easier and less expensive to deploy than wired networks. The wireless mesh networks typically include wired gateways that are wirelessly connected to wireless nodes, or wireless connected directly to client devices. Many wireless nodes can collectively provide a wireless mesh, in which client devices can associate with any of the wireless nodes.

Typically, the wireless nodes are implemented as wireless access points (APs). A typical wireless AP includes a local link interface to communicate with local client devices and a downlink and uplink interfaces to communicate with other APs. Conventional APs utilize the same communication frequency when communicating with other APs. As a result, there may be an interference between an uplink and a downlink communications and may have impact on the signal quality. In addition, communications between the wireless APs typically are in a form of plain text which may be vulnerable to be attacked.

SUMMARY OF THE DESCRIPTION

Techniques for secure communications among wireless mesh network access points are described herein. According to one embodiment, a wireless mesh network includes multiple wireless mesh access points communicatively coupled to each other via multiple mesh links and multiple end-user clients, each being associated with one of the wireless mesh access points. In response to a packet received at a first mesh access point of the wireless mesh access points from a local end-user client of the first mesh access point destined to another end-user client associated with a second mesh access point of the wireless mesh access points, the packet is routed via a tunneling protocol from the first mesh access point to the second mesh access point.

Other features of the present invention will be apparent from the accompanying drawings and from the detailed description which follows.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention is illustrated by way of example and not limitation in the figures of the accompanying drawings in which like references indicate similar elements.

FIG. 1 is a block diagram illustrating an example of a wireless mesh network configuration which may be used with an embodiment of the invention.

FIG. 2 is a block diagram illustrating inter-mesh AP communications according to one embodiment of the invention.

FIG. 3 is a block diagram illustrating an example of a wireless mesh access point according to one embodiment of the invention.

FIG. 4 is a block diagram illustrating an example of software architecture of a wireless mesh access point according to one embodiment of the invention.

FIG. 5 is a block diagram illustrating a data structure representing a routing table according to one embodiment of the invention.

FIG. 6 is a block diagram illustrating a data structure representing an interface mapping table according to one embodiment of the invention.

FIG. 7 is a block diagram illustrating a data packet used for tunneling according to one embodiment of the invention.

FIG. 8 is a flow diagram illustrating a process for routing a packet in a wireless mesh network according to one embodiment of the invention.

FIG. 9 is a flow diagram illustrating a process for routing a packet in a wireless mesh network according to another embodiment of the invention.

FIG. 10 illustrates a diagrammatic representation of a machine in the exemplary form of a computer system.

DETAILED DESCRIPTION

Techniques for secure communications among wireless mesh network access points are described herein. In the following description, numerous details are set forth to provide a more thorough explanation of embodiments of the present invention. It will be apparent, however, to one skilled in the art, that embodiments of the present invention may be practiced without these specific details. In other instances, well-known structures and devices are shown in block diagram form, rather than in detail, in order to avoid obscuring embodiments of the present invention.

Reference in the specification to “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the invention. The appearances of the phrase “in one embodiment” in various places in the specification do not necessarily all refer to the same embodiment.

According to certain embodiments of the invention, multiple wireless path design is provided for both backhaul (e.g., also referred to as a mesh link among multiple mesh APs) and user traffic (e.g., also referred to as a client link between an AP and a local end-user client) to eliminate adjacent AP signal interference degradation. There has been provided a best network throughput via layer 2 fast switching and bridging from AP (access point) to AP to support real time video, voice, and data applications. It is fully compatible with existing access servers, routers, and gateways since existing drivers and layer 3 applications are not modified. It is transparent to layer 3 and up protocols and thus, it is fully compatible with existing network infrastructure or equipments. An AP is directly connected to existing routers, gateways, or AP through, for example, 10/100 Ethernet. The management and security software architecture is configured to support Web based browser and SNMP (simple network management protocol). It also supports WEP (wireless encryption protocol) encryption security across wireless mesh network. Multiple APs can be coupled to each other based on a mesh ID assigned by a user or administrator.

In one embodiment, each node includes multiple wireless interfaces or antennas. For example, a node in a mesh network may include a local AP antenna that operates as an AP for local clients (e.g., end-user clients such as laptop computers, etc.) In addition, the node may further include multiple mesh link AP antennas, one for uplink and one for down link. An uplink interface is configured to communicate with a downlink interface of another node and likewise, a downlink interface of a node is configured to communicate with an uplink interface of another node. Separate channels (e.g., different communication frequencies) are used for uplink and downlink. As a result, air link interference can be greatly reduced.

According to another embodiment of the invention, software architecture utilizes existing wireless architecture such as IEEE 802.11 WiFi client and AP drivers, to achieve WIFi mesh network design. As a result, the system can maintain most of the features of WiFi client driver and WiFi access point driver so that it is fully compatible with certain third party products while creating a mesh WiFi network. For example, the software architecture includes an additional layer (also referred to herein as layer 2.5) between ordinary layer 2 and layer 3 of a network stack to process data received from layer 2 driver before delivering the data to ordinary layer 3 or alternatively, sending the data back down to layer 2 without sending the data to layer 3, dependent upon specific system design. As a result, third party layers 2 and 3 can be utilized without having to modify a specific driver of a third party vendors.

Further, according to a further embodiment, tunneling is designed to transfer data packets from one node to another node going through standard WiFi client and AP design. For example, each node includes a common AP interface to communicate with multiple clients, where each client communicates with the node via a tunneling technique using the common AP interface. Thus, when a node receive a data packet from a client via normal WiFi client/AP communication protocol, the specific data associated with the sender is encrypted using a variety of data encryption techniques and tunneled within the standard WiFi packets. The receiving node then may decrypt the data packets to reveal who is the actual sender. Further, each node that communicates with the AP interface of a particular node may appear as a virtual node in the particular node.

According to a further embodiment, each node in a WiFi mesh network includes a routing module (also referring to as a bridging module) and a database. The database is used to store information of other nodes which may be collected (e.g., learned) during communications with other nodes including, for example, signal strength, MAC (media access control) addresses, link status, and mesh links (e.g., parent and/or child nodes). The information stored in the database may be used to determine the best route to route the data packets. For example, each node may be assigned with a mesh ID by a user or an administrator. Under certain circumstances, only those nodes having the identical mesh ID may be grouped in a mesh network. Further, the signal strength information may be used to identify the adjacent nodes in the mesh network to determine the shortest route to an AP.

According another embodiment, if a first node has too many hop counts to a master node, and a second node has less hop counts, the first and second nodes may communicate with each other to “relocate” certain routes from the first node to the second node for the load balancing purposes. Note that the above techniques may be implemented in software, hardware, and a combination of both.

FIG. 1 is a block diagram illustrating an example of a wireless mesh network configuration which may be used with an embodiment of the invention. Referring to FIG. 1, wireless mesh network configuration 100 includes, but is not limited to, multiple mesh APs 103-106 communicatively coupled to each other as depicted via dash communication links. Some of the APs such as APs 103-104 may be coupled via a wired network to a gateway device 102 which allows traffic from the wireless mesh network to reach an external network or another network 101 such as wide area network (WAN), which may be the Internet.

Each of the APs 103-106 includes a local AP link to communicate with local clients (e.g., end-user clients) 107-114. Each of the clients 107-114 may be associated with any of the APs 103-106, which may be statically assigned by an administrator or alternatively, via roaming dynamically. In this example, clients 107-108 are associated with AP 103; clients 109-110 are associated with AP 105, clients 111- 112 are associated with AP 106; and clients 113-114 are associated with AP 104 respectively.

According to one embodiment, each of the APs 103-106 includes an uplink interface or antenna and a downlink interface or antenna. An uplink interface of one AP is used to communicate with a downlink interface of another AP. Similarly, a downlink interface of one AP is used to communicate with an uplink interface of another AP. For example, an up link interface of AP 105 may be used to communicate with a downlink interface of AP 103. Likewise, a downlink interface of AP 105 may be used to communicate with an uplink interface of AP 106.

According to one embodiment, communication frequencies for the uplink interface and downlink interface of a particular AP may be different which may be selected or configured by an administrator statically or dynamically (e.g., auto discovery or via frequency hopping). In this way, each backhaul communication link between two APs may have different frequency which greatly reduces the interference.

Furthermore, according to another embodiment, data between two APs may be securely communicated via a tunneling technique. For example, when an AP receives a packet from a local end-user client, the AP may tunnel the packet by encrypting at least the source and destination MAC (media access control) addresses as well as the payload of the packet into a payload of a new packet. The new packet is then package with a new set of source and destination MAC addresses, where the new source MAC address is associated with the AP itself while the destination MAC address is associated with another AP (e.g., next hop). As a result, the new packet can be layer-2 routed to the next AP identified by the new destination MAC address.

When the next hop AP receives the tunneled packet, the next hop AP strips out or removes the source and destination MAC addresses and decrypt the payload of the tunneled packet to reveal the original packet from the end user client. The next hop AP then examines the original destination MAC address to determine whether the destination end-user client is a local end-user client of the next hop AP. If the destination end-user client is a local end-user client, the original packet is transmitted to the identified local end-user client. If the destination end-user client is not a local end-user client, the AP then repackages or re-tunnels the original packet and sends the tunneled packet to another next hop AP, and so on.

FIG. 2 is a block diagram illustrating inter-mesh AP communications according to one embodiment of the invention. For example, APs 201-202 may be implemented as any of APs 103-106 of FIG. 1. Referring to FIG. 2, AP 201 includes an uplink interface 203 and a downlink interface 204, as well as a local link interface 205 for local clients 211. Similarly, AP 202 includes an uplink interface 207, a downlink interface 206, and a local link interface 208 for local clients 212. Downlink interface 204 of AP 201 is used to communicate with an uplink interface of a next hop 209. Uplink interface 207 of AP 202 is used to communicate with a downlink interface of a next hop 210. Uplink interface 203 is used to communicate with a downlink interface 206 of AP 202.

Typically, a local link interface communicates with a local client using a communication frequency of approximately 2.4 GHz using a standard wireless protocol such as, for example, IEEE 802.11b/g protocol. The communication frequency of the backhaul or mesh link communications is ranging approximately from 4.9 to 5.8 GHz using a standard wireless protocol such as, for example, IEEE 802.11a protocol. However, according to one embodiment, each mesh link may operate at a different communication frequency. For example, with respect to a particular AP, the communication frequency of a downlink interface is different than the communication frequency of an uplink interface. As a result, air interference is greatly reduced.

Furthermore, the communications between downlink interface 206 of AP 202 and uplink interface 203 of AP 201 are securely performed using a tunneling protocol and/or a variety of encryption techniques. For example, when AP 201 receives a packet form a local client 211, the AP 201 encrypts almost the entire packet to generate a new packet having a source MAC address of AP 201 and a destination MAC address of AP 202. The new packet is then routed from AP 201 to AP 202 via uplink interface 203 of AP 201 and downlink interface 206 of AP 202.

When AP 202 receives the new packet, AP 202 strips out the header (e.g., source and destination MAC addresses) and decrypts the payload of the new packet to reveal the original packet originated from end user client 211. Based on the destination MAC address of the revealed original packet, AP 202 determines whether the original packet is destined to a local end-user client such as client 212. If the original packet is destined to a local end-user client, AP 202 then routes the original packet to the local client via local link interface 208. However, if the original packet is not destined to a local end-user client, AP 202 may repackage or re-tunnel the original packet with a source MAC address of AP 202 and a destination MAC address of a next hop, which may be an AP communicatively coupled via uplink interface 207 or another AP communicatively coupled via downlink interface 206.

FIG. 3 is a block diagram illustrating an example of a wireless mesh access point according to one embodiment of the invention. For example, AP 300 may be implemented as part of AP 201 or AP 202 of FIG. 2. Referring to FIG. 3, in one embodiment, AP 300 includes, but is not limited to multiple wireless interface devices 301-304, also referred to herein as RF (radio frequency) or radio cards or devices, each having a corresponding wireless controller and necessary RF circuit, communicatively coupled to each other via bus or interconnect 307. The radio cards 301-304 may be provided by a third party vendor which also provides a software driver (e.g., layer 2 to layer 7 network driver). In this example, AP 300 includes an uplink interface card 301 that can be used to communicate with a downlink interface of another AP. AP 300 further includes a downlink interface card 302 that can be used to communicate with an uplink interface of another AP and a local link interface card 303 used to communicate with a local client. Furthermore, optionally, AP 300 includes a monitoring interface card 304 used to monitor or survey the mesh networks which may be used to reassign or balance the APs in the network such that the devices in the network can optimally operate.

AP 300 further includes one or more processors 305 coupled to the bus 307. In addition, AP 300 further includes a management interface 308 to allow a management station 309 to communicate with AP 300 over a network 310 for management purposes. The routing software (not shown) may be loaded within memory 306 and executed by processor 305. For example, each of the interface cards 301-304 may be configured by the management station 309 over network 310 to operate in a particular but different frequency to reduce air interference, etc. Each interface card may be assigned with a unique interface identifier (I/F ID) that uniquely identifies the corresponding interface, physically or logically (e.g., virtual). Other configurations may exist.

FIG. 4 is a block diagram illustrating an example of software architecture of a wireless mesh access point according to one embodiment of the invention. For example, software stack 400 may be running within memory 306 by processor 305 of FIG. 3. Referring to FIG. 4, software stack 400 includes, but is not limited to, layer 3 and up network stack 402 and layer 2 404 that can process data exchanged with hardware such as radio cards 405. Radio cards 405 may be implemented as any of the radio cards 301-304 as shown in FIG. 3. Note that layer 404 and layer 402 may be provided with the hardware 405 from a third party vendor.

In addition, according to one embodiment, software stack 400 further includes layer 403, also referred to as layer 2.5 logically representing an additional layer between layer 2 and layer 3 of OSI (open system interconnection). Layer 403 includes a routing logic 406 for routing data received from different radio cards via layer 404. Any data for management application such as SNMP (simple network management protocol) application 401 is routed via layer 402. In this embodiment, since layer 403 is inserted between layer 404 and 402, the ordinary layer 2 and layer 3 do not need to modify as layer 403 is completely transparent to layers 404 and 402.

The data is routed among multiple interfaces (e.g., uplink, downlink, or local link) based on information obtained from routing table 408 and/or interface mapping table 407. Interface mapping table 407 may be implemented in a manner similar to one as shown in FIG. 5. Likewise, routing table 408 may be implemented similar to one shown in FIG. 6.

Referring to FIG. 5, interface mapping table 500 includes multiple entries. Each entry includes an interface ID field 501, a source MAC address field 502, and a destination MAC address field 503. The interface ID field 501 is used to store an ID of a particular interface of the AP. The source MAC address field 502 is used to store a MAC address corresponding to an interface card (e.g., either uplink or downlink) identified by the interface ID stored in the interface ID field 501. The destination MAC address field 503 is used to store a MAC address of an interface card (e.g., either uplink or downlink) of a next hop AP device. The interface mapping table is used by the routing logic to tunnel a packet to a next hop.

Referring to FIG. 6, a routing table 600 includes multiple entries. Each entry includes a MAC address field 601 to store a particular MAC address (e.g., source or destination MAC address) and an interface ID field 602 to store an interface ID corresponding to a MAC address stored in MAC address field 601. This table is used to determine which interface card that a particular packet should be sent.

FIG. 7 is a block diagram illustrating a data packet used for tunneling according to one embodiment of the invention. Referring to FIG. 7, in this example, packet 701 is originally initiated from an end-user client such as client 211 of FIG. 2. In this example, like a standard TCP/IP packet, packet 701 includes, among others, a source MAC address 703, a destination MAC address, other layer-3 and up header 705, and payload 706.

Referring to FIGS. 2 and 7, when AP 201 receives packet 701 where AP is configured to maintain its own copy of interface mapping table (e.g., table 500 of FIG. 5) and a routing table (e.g., table 600 of FIG. 6), AP 201 may perform a lookup operation at the routing table to determine whether a source MAC address 703 (e.g., MAC address representing the end-user client 211) exists in the routing table. If not, AP 201 may store or insert a new entry into the routing table having the source MAC address 703 and an interface ID corresponding to an incoming interface of AP 201, in this example, interface 205.

In addition, according to one embodiment, AP 201 may further perform another lookup operation at the routing table based on the destination MAC address 704. It is assumed that an administrator initially has configured all the necessary routing paths in the mesh network. Thus, there should be an entry in the routing table having a MAC address corresponding to destination MAC address 704 associated with a particular interface (e.g., outgoing or egress interface) in the routing table. From the routing table, based on the destination MAC address 704, an outgoing interface ID is obtained that corresponds to, in this example, interface 203.

Further, according to one embodiment, AP 201 may further perform another lookup operation at the interface mapping table based on the interface ID obtained from the routing table to determine a pair of source MAC address 708 and destination MAC address 709, where the source MAC address 708 represents a MAC address associated with the outgoing interface of current AP and the destination MAC address 709 represents an ingress interface of a next hop AP. As a result, a new packet 702 is generated having source MAC address 708 and destination MAC address 709, where most of the original packet 701 having fields 703-706 is encrypted (e.g., tunneled) using a variety of encryption methods to generate a new payload 707 of pocket 702. Packet 702 is then transmitted to a next hop AP 202 via interface 203.

When AP 202 receives packet 702, AP 202 strips off the header having at least source MAC address 708 and destination MAC address 709 and decrypts payload 707 to reveal the original packet 701. Again, similar to operations performed by AP 201, AP 202 determines whether the revealed packet 701 is intended for its local end-user client such as client 212. If so, the revealed packet 701 is then transmitted to the local client. Otherwise, the packet 701 is then repackaged and tunneled to another AP using techniques similar to those set forth above. As a result, communications between two AP local networks can be securely performed.

Note that packets 701-702 are shown for purposes of illustration only. Other formats may also be applied. For example, instead of wrapping the original MAC addresses of the packet 701 using the AP MAC addresses to generate packet 702, the original MAC addresses of packet 701 may be replaced by the AP MAC addresses. The original MAC addresses may be relocated to some other locations such as the end of packet 702.

FIG. 8 is a flow diagram illustrating a process for routing a packet in a wireless mesh network according to one embodiment of the invention. Note that process 800 may be performed by processing logic which may include hardware, software, or a combination of both. For example, process 800 may be performed by a wireless mesh AP such as AP 300 of FIG. 3. Referring to FIG. 8, at block 801, a first packet (e.g., packet 701 of FIG. 7) is received via an incoming or ingress interface (e.g., local link interface) from a local end-user client having a source MAC address representing the local end-user client and a destination MAC address representing a destination end-user client.

At block 802, an outgoing or egress interface (e.g., interface ID) is determined based on the destination MAC address of the first packet. For example, the egress interface ID may be determined via a lookup operation of a routing table maintained within the respective AP (e.g., routing table 600 of FIG. 6). At block 803, if the source MAC address of the first packet does not exist in the routing table, a new entry is created in the routing table for storing the source MAC address and an interface ID corresponding to an interface from which the first packet is received.

At block 804, based on the egress interface ID determined above, an AP source MAC address and an AP destination MAC address are determined. For example, the AP source and destination MAC addresses may be determined via a lookup operation on the interface mapping table maintained within the respective AP (e.g., table 500 of FIG. 5). At block 805, a new packet or a second packet (e.g., packet 702 of FIG. 7) is created using the AP source and destination MAC address by tunneling the first packet, including encrypting at least the source and destination MAC addresses as well as the payload of the first packet. Thereafter, at block 806 the new packet is transmitted to a proper interface identified by the interface ID, which is then routed to a next hop AP.

FIG. 9 is a flow diagram illustrating a process for routing a packet in a wireless mesh network according to another embodiment of the invention. Note that process 900 may be performed by processing logic which may include hardware, software, or a combination of both. For example, process 900 may be performed by a wireless mesh AP such as AP 300 of FIG. 3. Referring to FIG. 9, at block 901, a first packet is received via an incoming or ingress interface from a previous hop AP, the first packet having a first source MAC address and a first destination MAC address, as well as a payload. The first source MAC address is associated with an egress interface of the previous hop AP and the destination MAC address is associated with an ingress interface of the current hop AP. Note that the ingress interface of the current hop AP may be an uplink interface or a downlink interface. Similarly, an egress interface of a previous hop AP may be an uplink interface or a downlink interface.

At block 902, the source and destination MAC addresses of the first packet is stripped off and the payload is decrypted to reveal a second packet that has been tunneled within the first packet. The second packet includes a second source MAC address associated with a first end-user client (e.g., original end-user client that initiates the first packet form a local link) and a destination MAC address associated with a second end-user client as a destination end-user client intended to receive the first packet.

At block 903, it is determined whether the second packet is intended to a local end-user client of a current hop AP (e.g., whether the second end-user client is a local end-user client). For example, a lookup operation may be performed at a routing table maintained by the current hop AP based on the destination MAC address of the second packet (e.g., whether an interface ID corresponding to the destination MAC address of the second packet represents a local link interface of a current hop AP). If the second packet is intended to a local end-user client of a current hop AP, at block 904, the second packet is transmitted to the intended local end-user client via a local link interface of the current hop AP.

If the second packet is not intended to a local end-user client of a current hop AP, at block 905, the second packet is then tunneled within a third packet, and the third packet is then transmitted to a next hop AP using techniques similar to those set forth above. Other operations may also be performed.

FIG. 10 illustrates a diagrammatic representation of a machine in the exemplary form of a computer system within which a set of instructions, for causing the machine to perform any one or more of the methodologies discussed herein, may be executed. In alternative embodiments, the machine may be connected (e.g., networked) to other machines in a Local Area Network (LAN), an intranet, an extranet, or the Internet. The machine may operate in the capacity of a server or a client machine in a client-server network environment, or as a peer machine in a peer-to-peer (or distributed) network environment. The machine may be a personal computer (PC), a tablet PC, a set-top box (STB), a Personal Digital Assistant (PDA), a cellular telephone, a web appliance, a server, a network router, switch or bridge, or any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine. Further, while only a single machine is illustrated, the term “machine” shall also be taken to include any collection of machines (e.g., computers) that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein.

The system 1000 may be used as a client, a server, a gateway device, or a wireless mesh access point described above. For example, system 1000 may be implemented as part of any of gateway 102, clients 107-114, or APs 103-106 of FIG. 1 or alternatively, management system 309 of FIG. 3.

As shown in FIG. 10, the system 1000, which is a form of a data processing system, includes a bus or interconnect 1002 which is coupled to one or more microprocessors 1003 and a ROM 1007, a volatile RAM 1005, and a non-volatile memory 1006. The microprocessor 1003 is coupled to cache memory 1004 as shown in the example of FIG. 10. Processor 1003 may be, for example, a PowerPC microprocessor or an Intel compatible processor. Alternatively, processor 1003 may be a digital signal processor or processing unit of any type of architecture, such as an ASIC (Application-Specific Integrated Circuit), a CISC (Complex Instruction Set Computing), RISC (Reduced Instruction Set Computing), VLIW (Very Long Instruction Word), or hybrid architecture, although any appropriate processor may be used.

The bus 1002 interconnects these various components together and also interconnects these components 1003, 1007, 1005, and 1006 to a display controller and display device 1008, as well as to input/output (I/O) devices 1010, which may be mice, keyboards, modems, network interfaces, printers, and other devices which are well-known in the art.

Typically, the input/output devices 1010 are coupled to the system through input/output controllers 1009. The volatile RAM 1005 is typically implemented as dynamic RAM (DRAM) which requires power continuously in order to refresh or maintain the data in the memory. The non-volatile memory 1006 is typically a magnetic hard drive, a magnetic optical drive, an optical drive, or a DVD RAM or other type of memory system which maintains data even after power is removed from the system. Typically, the non-volatile memory will also be a random access memory, although this is not required.

While FIG. 10 shows that the non-volatile memory is a local device coupled directly to the rest of the components in the data processing system, embodiments of the present invention may utilize a non-volatile memory which is remote from the system; such as, a network storage device which is coupled to the data processing system through a network interface such as a modem or Ethernet interface. The bus 1002 may include one or more buses connected to each other through various bridges, controllers, and/or adapters, as is well-known in the art. In one embodiment, the I/O controller 1009 includes a USB (Universal Serial Bus) adapter for controlling USB peripherals. Alternatively, I/O controller 1009 may include an IEEE-1394 adapter, also known as FireWire adapter, for controlling FireWire devices.

Thus, techniques for secure communications among wireless mesh network access points have been described herein. Some portions of the preceding detailed descriptions have been presented in terms of algorithms and symbolic representations of operations on data bits within a computer memory. These algorithmic descriptions and representations are the ways used by those skilled in the data processing arts to most effectively convey the substance of their work to others skilled in the art. An algorithm is here, and generally, conceived to be a self-consistent sequence of operations leading to a desired result. The operations are those requiring physical manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated. It has proven convenient at times, principally for reasons of common usage, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, or the like.

It should be borne in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless specifically stated otherwise as apparent from the above discussion, it is appreciated that throughout the description, discussions utilizing terms such as “processing” or “computing” or “calculating” or “determining” or “displaying” or the like, refer to the action and processes of a computer system, or similar electronic computing device, that manipulates and transforms data represented as physical (electronic) quantities within the computer system's registers and memories into other data similarly represented as physical quantities within the computer system memories or registers or other such information storage, transmission or display devices.

Embodiments of the present invention also relate to an apparatus for performing the operations herein. This apparatus may be specially constructed for the required purposes, or it may comprise a general-purpose computer selectively activated or reconfigured by a computer program stored in the computer. Such a computer program may be stored in a computer readable storage medium, such as, but is not limited to, any type of disk including floppy disks, optical disks, CD-ROMs, and magnetic-optical disks, read-only memories (ROMs), random access memories (RAMs), erasable programmable ROMs (EPROMs), electrically erasable programmable ROMs (EEPROMs), magnetic or optical cards, or any type of media suitable for storing electronic instructions, and each coupled to a computer system bus.

The algorithms and displays presented herein are not inherently related to any particular computer or other apparatus. Various general-purpose systems may be used with programs in accordance with the teachings herein, or it may prove convenient to construct more specialized apparatus to perform the required method operations. The required structure for a variety of these systems will appear from the description below. In addition, embodiments of the present invention are not described with reference to any particular programming language. It will be appreciated that a variety of programming languages may be used to implement the teachings of embodiments of the invention as described herein.

A machine-readable medium may include any mechanism for storing or transmitting information in a form readable by a machine (e.g., a computer). For example, a machine-readable medium includes read only memory (“ROM”); random access memory (“RAM”); magnetic disk storage media; optical storage media; flash memory devices; electrical, optical, acoustical or other form of propagated signals (e.g., carrier waves, infrared signals, digital signals, etc.); etc.

In the foregoing specification, embodiments of the invention have been described with reference to specific exemplary embodiments thereof. It will be evident that various modifications may be made thereto without departing from the broader spirit and scope of the invention as set forth in the following claims. The specification and drawings are, accordingly, to be regarded in an illustrative sense rather than a restrictive sense. 

1. A method for routing data in a wireless mesh network, the method comprising: receiving a first packet at a first wireless mesh access point (AP), the first wireless mesh AP being one of a plurality wireless mesh APs of the wireless mesh network, wherein each of the wireless mesh APs includes a mesh link interface to communicate with each other and a local link interface to communicate with a local client of each wireless mesh AP; determining an interface identifier (ID) based on a destination media access control (MAC) address of the first packet; transmitting the first packet via the local link interface to a local client if the first packet is intended to the local client based on the interface ID; determining an AP source MAC address and an AP destination MAC address based on the interface ID by performing a lookup operation in an interface mapping table, the interface mapping table including a plurality entries, each entry including an interface ID associated with an AP source MAC address of an egress mesh link interface corresponding to the interface ID and an AP destination MAC address of an ingress mesh link interface of a second wireless mesh AP; and transmitting at least a payload of the first packet to the second wireless mesh AP via the mesh link interface using a secure tunnel established between the first and second wireless mesh APs based on the AP source MAC address and the AP destination MAC address obtained from the interface mapping table, if the first packet is not intended to the local client of the first wireless mesh AP, wherein at least the payload of the first packet is routed using a layer-2 switching protocol.
 2. The method of claim 1, further comprising determining whether the first packet is intended for the local client based on a destination media access control (MAC) address of the first packet, wherein the first packet is intended for the local client if the destination MAC address matches a MAC address of the local client.
 3. The method of claim 1, wherein determining an interface ID based on the destination MAC address of the first packet comprises: maintaining a routing table within the first wireless mesh AP having a plurality entries, each entry including a MAC address associated with an interface identifier (ID) uniquely identifying one of the local link interface and the mesh link interface of the first wireless mesh AP; and performing a lookup operation in the routing table to determine the interface ID corresponding to the destination MAC address of the first packet, wherein the first packet is intended for the local client if the interface ID corresponds to the local link interface.
 4. A method for routing data in a wireless mesh network, the method comprising: receiving a first packet at a first wireless mesh access point (AP), the first wireless mesh AP being one of a plurality wireless mesh APs of the wireless mesh network, wherein each of the wireless mesh APs includes a mesh link interface to communicate with each other and a local link interface to communicate with a local client of each wireless mesh AP; determining an interface ID corresponding to the destination MAC address of the first packet by performing a lookup operation in a routing table, the routing table having a plurality entries, each entry including a MAC address associated with an interface identifier (ID) uniquely identifying one of the local link interface and the mesh link interface of the first wireless mesh AP; transmitting the first packet via the local link interface to a local client if the first packet is intended to the local client; if the first packet is not intended for a local client, performing a lookup operation in an interface mapping table to determine AP source and destination MAC addresses based on the interface ID, the interface mapping table including a plurality entries, each entry including an interface ID associated with an AP source MAC address of an egress mesh link interface corresponding to the interface ID and an AP destination MAC address of an ingress mesh link interface of a second wireless mesh AP; and transmitting at least a payload of the first packet to the second wireless mesh AP via the mesh link interface using a secure tunnel established between the first and second wireless mesh APs based on the AP source and destination MAC addresses obtained from the interface mapping table, wherein at least the payload of the first packet is routed using a layer-2 switching protocol.
 5. The method of claim 4, further comprising: encrypting at least a payload, the source MAC address, and the destination MAC address of the first packet into an encrypted first packet; generating a second packet having the encrypted first packet as a payload of the second packet, wherein the second packet is represented by the AP source and destination MAC addresses obtained from the interface mapping table; and transmitting the second packet to the second wireless mesh AP over the mesh link.
 6. The method of claim 1, further comprising: receiving a third packet having the first packet encrypted therein, wherein the third packet is received from a third wireless mesh AP; and stripping off a header of the third packet and decrypting a payload of the third packet to reveal the first packet, prior to determining whether the first packet is intended for the local client.
 7. A non-transitory machine-readable storage medium having instructions stored therein, which when executed by a processor, cause the process to perform a method for routing data in a wireless mesh network, the method comprising: receiving a first packet at a first wireless mesh access point (AP), the first wireless mesh AP being one of a plurality wireless mesh APs of the wireless mesh network, wherein each of the wireless mesh APs includes a mesh link interface to communicate with each other and a local link interface to communicate with a local client of each wireless mesh AP; determining an interface identifier (ID) based on a destination media access control (MAC) address of the first packet; transmitting the first packet via the local link interface to a local client if the first packet is intended to the local client based on the interface ID; determining an AP source MAC address and an AP destination MAC address based on the interface ID by performing a lookup operation in an interface mapping table, the interface mapping table including a plurality entries, each entry including an interface ID associated with an AP source MAC address of an egress mesh link interface corresponding to the interface ID and an AP destination MAC address of an ingress mesh link interface of a second wireless mesh AP; and transmitting at least a payload of the first packet to the second wireless mesh AP via the mesh link interface using a secure tunnel established between the first and second wireless mesh APs based on the AP source MAC address and the AP destination MAC address obtained from the interface mapping table, if the first packet is not intended to the local client of the first wireless mesh AP, wherein at least the payload of the first packet is routed using a layer-2 switching protocol.
 8. The non-transitory machine-readable storage medium of claim 7, wherein the method further comprises determining whether the first packet is intended for the local client based on a destination media access control (MAC) address of the first packet, wherein the first packet is intended for the local client if the destination MAC address matches a MAC address of the local client.
 9. The non-transitory machine-readable storage medium of claim 7, wherein determining an interface ID based on the destination MAC address of the first packet comprises: maintaining a routing table within the first wireless mesh AP having a plurality entries, each entry including a MAC address associated with an interface identifier (ID) uniquely identifying one of the local link interface and the mesh link interface of the first wireless mesh AP; and performing a lookup operation in the routing table to determine the interface ID corresponding to the destination MAC address of the first packet, wherein the first packet is intended for the local client if the interface ID corresponds to the local link interface.
 10. The non-transitory machine-readable storage medium of claim 9, wherein the method further comprises: encrypting at least a payload, the source MAC address, and the destination MAC address of the first packet into an encrypted first packet; generating a second packet having the encrypted first packet as a payload of the second packet, wherein the second packet is represented by the AP source and destination MAC addresses obtained from the interface mapping table; and transmitting the second packet to the second wireless mesh AP over the mesh link.
 11. The non-transitory machine-readable storage medium of claim 7, wherein the method further comprises: receiving a third packet having the first packet encrypted therein, wherein the third packet is received from a third wireless mesh AP; and stripping off a header of the third packet and decrypting a payload of the third packet to reveal the first packet, prior to determining whether the first packet is intended for the local client.
 12. A wireless mesh access point (AP), comprising: an ingress interface to receive a first packet, the ingress interface being one of a mesh link interface for coupling with another wireless mesh AP and a local link interface for coupling one or more local clients; an egress interface being one of a mesh link interface for coupling with another wireless mesh AP and a local link interface for coupling one or more local clients; a memory to store an interface mapping table having a plurality entries, each entry including an interface identifier (ID) associated with an AP source MAC address of an egress mesh link interface corresponding to the interface ID and an AP destination MAC address of an ingress mesh link interface of the second wireless mesh AP; a routing module coupled the ingress and egress interfaces to determine an interface ID corresponding to a destination MAC address of the first packet, to transmit the first packet via the egress interface to a local client if the first packet is intended to the local client based on the interface ID, to perform a lookup operation in the interface mapping table to determine AP source and destination MAC addresses corresponding to the interface ID, and to transmit at least a payload of the first packet via the egress interface to a second wireless mesh AP using a secure tunnel established with the second wireless mesh AP based on the AP source and destination MAC addresses, if the first packet is not intended to the local client, wherein at least the payload of the first packet is routed using a layer-2 switching protocol.
 13. The wireless mesh AP of claim 12, wherein the routing module is configured to determine whether the first packet is intended for the local client based on a destination media access control (MAC) address of the first packet, wherein the first packet is intended for the local client if the destination MAC address matches a MAC address of the local client.
 14. The wireless mesh AP of claim 12, wherein the memory further stores a routing table having a plurality entries, each entry including a MAC address associated with an interface identifier (ID) uniquely identifying one of the local link interface and the mesh link interface, wherein the routing module is configured to perform a lookup operation in the routing table to determine the interface ID corresponding to the destination MAC address of the first packet, wherein the first packet is intended for the local client if the interface ID corresponds to the local link interface.
 15. The wireless mesh AP of claim 14, wherein the routing module is configured to encrypt at least a payload, the source MAC address, and the destination MAC address of the first packet into an encrypted first packet, generate a second packet having the encrypted first packet as a payload of the second packet, wherein the second packet is represented by the AP source and destination MAC addresses obtained from the interface mapping table, and transmit the second packet to another wireless mesh AP.
 16. The wireless mesh AP of claim 12, wherein the ingress interface receives a third packet having the first packet encrypted therein, wherein the third packet is received from a third wireless mesh AP, and wherein the routing module is configured to strip off a header of the third packet and decrypting a payload of the third packet to reveal the first packet, prior to determining whether the first packet is intended for the local client. 